Flow control system and method

ABSTRACT

A method, computer program product, and computing system for monitoring a plurality of dataflows within a wired communication trunk for the occurrence of one or more conditions. In response to the occurrence of the one or more conditions, a rate of at least one dataflow chosen from the plurality of dataflows is adjusted.

RELATED APPLICATION(S)

This application claims the benefit of the following U.S. Provisional Application No. 62/232,827 filed on 25 Sep. 2015, 62/342,486 filed on 27 May 2016, 62/342,506 filed on 27 May 2016, 62/342,499 filed on 27 May 2016, and 62/342,493 filed on 27 May 2016; their contents of which are incorporated herein by reference.

TECHNICAL FIELD

This disclosure relates to data communication systems and, more particularly, to data communication systems that control the individual dataflows contained therein.

BACKGROUND

The transmission, storing and safeguarding of electronic content is of paramount importance in modern business specifically and the modern world generally. Accordingly, various systems and methodologies may be employed to transmit, store and safeguard such electronic content.

Such electronic content may be transferred between users/locations via one or more data networks, examples of which may include but are not limited to private networks and public networks. Unfortunately, the current manner in which this packetized data is moved within/across these networks often result in erratic and unpredictable network behavior, wherein packets are lost and dataflow rates are drastically reduced in response to the same.

SUMMARY OF DISCLOSURE

In one implementation, a computer-implemented method is executed on a computing device and includes monitoring a plurality of dataflows within a wired communication trunk for the occurrence of one or more conditions. In response to the occurrence of the one or more conditions, a rate of at least one dataflow chosen from the plurality of dataflows is adjusted.

One or more of the following features may be included. Adjusting a rate of at least one dataflow chosen from the plurality of dataflows may include increasing the rate of the at least one dataflow. Increasing the rate of the at least one dataflow may include one or more of: increasing an RWND value associated with the at least one dataflow; and decreasing an acknowledgement delay associated with the at least one dataflow. Adjusting a rate of at least one dataflow chosen from the plurality of dataflows may include decreasing the rate of the at least one dataflow. Decreasing the rate of the at least one dataflow may include one or more of: decreasing an RWND value associated with the at least one dataflow; and increasing an acknowledgement delay associated with the at least one dataflow. The occurrence of the one or more conditions may include the loss of packets between a sending device of the at least one dataflow and the wired communication trunk. The occurrence of the one or more conditions may include the loss of packets between a receiving device of the at least one dataflow and the wired communication trunk. The occurrence of the one or more conditions may include the storing of packets of the at least one dataflow within a gateway coupled to the wired communication trunk. An actual bandwidth utilization of the wired communication trunk may be determined. The occurrence of the one or more conditions may include the actual bandwidth utilization of the wired communication trunk exceeding a target bandwidth utilization for the wired communication trunk.

In another implementation, a computer program product resides on a computer readable medium and has a plurality of instructions stored on it. When executed by a processor, the instructions cause the processor to perform operations including monitoring a plurality of dataflows within a wired communication trunk for the occurrence of one or more conditions. In response to the occurrence of the one or more conditions, a rate of at least one dataflow chosen from the plurality of dataflows is adjusted.

One or more of the following features may be included. Adjusting a rate of at least one dataflow chosen from the plurality of dataflows may include increasing the rate of the at least one dataflow. Increasing the rate of the at least one dataflow may include one or more of: increasing an RWND value associated with the at least one dataflow; and decreasing an acknowledgement delay associated with the at least one dataflow. Adjusting a rate of at least one dataflow chosen from the plurality of dataflows may include decreasing the rate of the at least one dataflow. Decreasing the rate of the at least one dataflow may include one or more of: decreasing an RWND value associated with the at least one dataflow; and increasing an acknowledgement delay associated with the at least one dataflow. The occurrence of the one or more conditions may include the loss of packets between a sending device of the at least one dataflow and the wired communication trunk. The occurrence of the one or more conditions may include the loss of packets between a receiving device of the at least one dataflow and the wired communication trunk. The occurrence of the one or more conditions may include the storing of packets of the at least one dataflow within a gateway coupled to the wired communication trunk. An actual bandwidth utilization of the wired communication trunk may be determined. The occurrence of the one or more conditions may include the actual bandwidth utilization of the wired communication trunk exceeding a target bandwidth utilization for the wired communication trunk.

In another implementation, a computing system including a processor and memory is configured to perform operations including monitoring a plurality of dataflows within a wired communication trunk for the occurrence of one or more conditions. In response to the occurrence of the one or more conditions, a rate of at least one dataflow chosen from the plurality of dataflows is adjusted.

One or more of the following features may be included. Adjusting a rate of at least one dataflow chosen from the plurality of dataflows may include increasing the rate of the at least one dataflow. Increasing the rate of the at least one dataflow may include one or more of: increasing an RWND value associated with the at least one dataflow; and decreasing an acknowledgement delay associated with the at least one dataflow. Adjusting a rate of at least one dataflow chosen from the plurality of dataflows may include decreasing the rate of the at least one dataflow. Decreasing the rate of the at least one dataflow may include one or more of: decreasing an RWND value associated with the at least one dataflow; and increasing an acknowledgement delay associated with the at least one dataflow. The occurrence of the one or more conditions may include the loss of packets between a sending device of the at least one dataflow and the wired communication trunk. The occurrence of the one or more conditions may include the loss of packets between a receiving device of the at least one dataflow and the wired communication trunk. The occurrence of the one or more conditions may include the storing of packets of the at least one dataflow within a gateway coupled to the wired communication trunk. An actual bandwidth utilization of the wired communication trunk may be determined. The occurrence of the one or more conditions may include the actual bandwidth utilization of the wired communication trunk exceeding a target bandwidth utilization for the wired communication trunk.

The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic view of a wired communication platform and a control process;

FIG. 2 is a flow chart of one embodiment of the control process of FIG. 1;

FIG. 3 is a diagrammatic view of a procedure implemented by the control process of FIG. 1;

FIG. 4 is a diagrammatic view of another procedure implemented by the control process of FIG. 1;

FIG. 5 is a flow chart of another embodiment of the control process of FIG. 1;

FIG. 6 is a diagrammatic view of another embodiment of the wired communication platform of FIG. 1;

FIG. 7 is a flow chart of another embodiment of the control process of FIG. 1;

FIG. 8 is a diagrammatic view of another embodiment of the wired communication platform of FIG. 1; and

FIG. 9 is a flow chart of another embodiment of the control process of FIG. 1.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Standard Communication Platform

In standard TCP communication platforms today, a SYN packet may be transmitted and in a Round Trip Time a SYN-ACK packet may be received to confirm receipt of the SYN packet. Once received, two data packets may be transmitted and in a Round Trip Time an ACK packet may be received, thus allowing for the transmission of four data packets. And as long as no errors are encountered, the quantity of data packets transmitted per burst may continue to double every Round Trip Time.

However, when the network and/or the receiving device overloads, one or more data packets may be lost, which may signal the sending device to implement various operations (e.g., reducing their transmission rate by 50% and/or changing to a slower rate of increase). Unfortunately, the transmission rate will still be increased over time . . . and the network and/or the receiving device will once again overload. Further, when the sending device launched the burst of data packets that resulted in the network and/or the receiving device overloading, this burst would typically be a large quantity of data packets that was sent at twice the prior transmission rate, resulting in the loss of a large quantity of data packets. Further complicating the situation is that recovering from such a large data packet loss may be difficult and may further overload the network and/or receiving device. This situation may cause more overloads, more lost data packets, and more 50% reductions in transmission rate, resulting in a saw tooth data transmission waveform having a cycle that is equal to the amount of time that it takes for the data transfer rate to increase to the point of overload and reset.

High-Speed Communication Platform:

Referring to FIG. 1, there is shown communication platform 10. Communication platform 10 may include wired communication trunk 12 having a first end (e.g., first end 14) and a second end (e.g., second end 16). First acknowledgement device 18 may be coupled to first end 14 of wired communication trunk 12 and second acknowledgement device 20 may be coupled to second end 16 of wired communication trunk 12. An example of first acknowledgement device 18 and second acknowledgement device 20 may include but is not limited to a gateway. Examples of wired communication trunk 12 may include: an electrical communication trunk (e.g., a communication trunk in which data is transmitted as electrical signals); an optical communication trunk (e.g., a communication trunk in which data is transmitted as optical signals); and a submarine cable (e.g., an underwater communication trunk in which data is transmitted as electrical and/or optical signals).

First router/switch 22 may be coupled to first acknowledgement device 18 (e.g., a gateway) and sending device 24 may be coupled to first router/switch 22. Second router/switch 26 may be coupled to second acknowledgement device 20 (e.g., a gateway) and receiving device 28 may be coupled to second router/switch 26. Examples of sending device 24 and receiving device 28 may include but are not limited to a personal electronic device, a general purpose computing device, a server computer, and a series of server computers.

As is known in the art, when data is transferred between e.g., sending device 24 and receiving device 28, various messages and data packets may be transferred between devices 24, 28. For example, assume that sending device 24 wishes to communicate with receiving device 28. Accordingly, a dataflow (e.g., dataflow 30) may need to be established between sending device 24 and receiving device 28.

In order to establish dataflow 30, a triple handshake procedure may be employed, wherein sending device 24 may send a packet (e.g., synchronize (SYN) packet 32) to receiving device 28; synchronization acknowledgement (SYN-ACK) packet 34 may be received by sending device 24; and sending device 24 may send acknowledgement (ACK) packet 36 to receiving device 28; thus establishing dataflow 30.

In a traditional (i.e., prior art) communication platform that does not include first acknowledgement device 18 and second acknowledgement device 20, synchronization acknowledgement (SYN-ACK) packet 34 would need to be generated by receiving device 28, resulting in poor performance and lackadaisical response times. For example, assume that the time-of-flight delay between sending device 24 and first acknowledgement device 18 in 1.0 milliseconds, the time-of-flight delay between first acknowledgement device 18 and second acknowledgement device 20 is 30.0 milliseconds, and the time-of-flight delay between second acknowledgement device 20 and receiving device 28 is also 1.0 milliseconds. Accordingly, when SYN packet 32 is transmitted by sending device 24, it would take 32.0 milliseconds for SYN packet 32 to reach receiving device 28. Assuming that upon receiving SYN packet 32, receiving device 28 transmits SYN-ACK packet 34 to sending device 24, which would take 32.0 milliseconds to arrive. Accordingly, the quantity of time between sending device 24 transmitting SYN packet 32 and sending device 24 receiving SYN-ACK packet 34 is 64.0 milliseconds.

However and as discussed above, communication platform 10 includes first acknowledgement device 18 and second acknowledgement device 20. Accordingly and in communication platform 10, when SYN packet 32 is generated and transmitted by sending device 24 and is received by first acknowledgement device 18, first acknowledgement device 18 may transmit SYN packet 32 to second acknowledgement device 20 (en route to receiving device 28). First acknowledgement device 18 may also generate SYN-ACK packet 34 and transmit the same to sending device 24. In this particular example and configuration, SYN-ACK packet 34 will be received by sending device 24 2.0 milliseconds after the transmission of SYN packet 32 (as opposed to 64.0 milliseconds after the transmission of SYN packet 32 in the traditional (i.e., prior art) communication platform).

First acknowledgement device 18 may be configured to store a copy of SYN packet 32. Upon SYN packet 32 reaching receiving device 28, receiving device 28 may also generate and transmit a SYN-ACK packet (e.g., SYN-ACK packet 34′). However, upon SYN-ACK packet 34′ being received by first acknowledgement device 18, SYN-ACK packet 34′ may be discarded (as SYN-ACK packet 34 was already sent to sending device 24 by first acknowledgement device 18). Further, the copy of SYN packet 32 that was stored within first acknowledgement device 18 may be deleted (as it is no longer needed since SYN-ACK packet 34′ confirmed that SYN packet 32 was received by receiving device 28).

While the above-discussion concerns SYN packet 32 being processed by first acknowledgement device 18 and SYN-ACK packet 34 being generated by first acknowledgement device 18, this is for illustrative purposes only and is but one example of the manner is which the SYN, SYN-ACK, ACK process may be implemented on communication platform 10. And while such a configuration may result in a considerable increase in responsiveness (i.e., a 2.0 millisecond loop time as opposed to a 64.0 millisecond loop time), communication platform 10 may be configured so that SYN packet 32 is only processed by receiving device 28 resulting in a loop time of 64.0 milliseconds. However, subsequent transmissions of data packets would indeed be processed by first acknowledgement device 18 and their related acknowledgement (ACK) packets would be generated by first acknowledgement device 18, thus resulting in the above-described 64.0 millisecond to 2.0 millisecond loop time reduction.

Flow Control Methodology:

During operation of communication platform 10, at any given time, a plurality of dataflows (e.g., plurality of dataflows 38) may be present within wired communication trunk 12, wherein the particular bandwidth being consumed by each dataflow included within plurality of dataflows 38 may vary during utilization. For example, if dataflow 30 is established to transfer a file (e.g., file 38) from sending device 24 to receiving device 28, the bandwidth consumed by dataflow 30 may initially be slow as the above-described SYN, SYN-ACK, ACK procedure is performed, wherein the bandwidth consumed by dataflow 30 may be increased until reaching a transfer limit (as will be described below) and maintained until the transfer of file 38 is complete.

Referring also to FIG. 2, one or more of first acknowledgement device 18 and second acknowledgement device 20 may execute control process 50, wherein control process 50 may be configured to regulate the bandwidth of each dataflow included within plurality of flows 38.

The instruction sets and subroutines of control process 50, which may be stored on a storage device (e.g., storage device 52, 54) included within first acknowledgement device 18 and/or second acknowledgement device 20 (respectively), may be executed by one or more processors (not shown) and one or more memory architectures (not shown) included within first acknowledgement device 18 and/or second acknowledgement device 20. Examples of storage device 52, 54 may include but are not limited to: a hard disk drive; a random access memory (RAM); a read-only memory (ROM); and all forms of flash memory storage devices.

During operation of communication platform 10, control process 50 may monitor 100 a plurality of dataflows (e.g., plurality of dataflows 38) within wired communication trunk 12 for the occurrence of one or more conditions that may e.g., indicate the need to adjust the bandwidth of one or more of the flows included within plurality of flows 38. Accordingly and in response to the occurrence of these one or more conditions, control process 50 may adjust 102 a rate of at least one dataflow chosen from the plurality of dataflows (e.g., plurality of dataflows 38). As will be discussed below in greater detail and depending upon whether the occurrence is a systemic occurrence or a discrete occurrence, these adjustments may be made to all of the dataflows within e.g., plurality of dataflows 38; or may be made to one or more discrete dataflows within e.g., plurality of dataflows 38.

An example of a discrete occurrence may include but is not limited to: the loss of data packets between sending device 24 of a discrete dataflow (e.g., dataflow 30) and wired communication trunk 12 (e.g., first acknowledgement device 18); the loss of data packets between receiving device 28 of a discrete dataflow (e.g., dataflow 30) and wired communication trunk 12 (e.g., second acknowledgement device 20); and the storing of data packets of a discrete dataflow (e.g., dataflow 30) within a gateway coupled to wired communication trunk 12. An example of a systemic occurrence may include but is not limited to the actual bandwidth utilization of wired communication trunk 12 exceeding a target bandwidth utilization for wired communication trunk 12.

When adjusting 102 a rate of at least one dataflow (e.g., dataflow 30) chosen from plurality of dataflows 38, control process 50 may increase 104 the rate of the at least one dataflow (e.g., dataflow 30). Alternatively and when adjusting 102 a rate of at least one dataflow (e.g., dataflow 30) chosen from plurality of dataflows 38, control process 50 may decrease 106 the rate of the at least one dataflow (e.g., dataflow 30).

For the following example, dataflow 30 will be adjusted 102 and the manner in which dataflow 30 is increased 104 and/or decreased 106 shall be discussed. As discussed above and continuing with the example in which sender 24 is sending file 38 to receiver 28, the above-described SYN, SYN-ACK, ACK procedure may be utilized to establish dataflow 30. Once dataflow 30 is established, the process of transferring file 38 from sending device 24 to receiving device 28 may begin.

Typically and in accordance with standard IP operations, sending device 24 may ramp up their transfer rate through the successive doubling of the quantity of packets transferred in a single operation. For example, sending device 24 may first send one data packet . . . and once acknowledged may send two data packets . . . and once acknowledged may send four data packets . . . and once acknowledged may send eight data packets . . . and once acknowledged may send sixteen data packets . . . and once acknowledged may send thirty-two data packets . . . and once acknowledged may send sixty-four data packets . . . and once acknowledged may send one-hundred-twenty-eight data packets . . . and so on. At a certain transfer rate, this repeated doubling of the transfer rate may be slowed to a slower rate of increase.

Unfortunately and in a traditional (i.e., prior art) communication platform that does not include first acknowledgement device 18 and second acknowledgement device 20, this increasing of transfer rates (be it doubling or at a lesser level) would continue to occur until packet loss occur, at which point the transfer rate of dataflow 30 may be reduced by 50%.

However, as communication platform 10 includes first acknowledgement device 18 and second acknowledgement device 20, the rate of dataflow 30 (and the dataflows included within plurality of dataflows 38) may be individually controlled. Generally speaking and as will be discussed below in greater detail, control process 50 may be configured to control the transfer rate of discrete dataflows (e.g., dataflow 30) through the use of an RWND value and acknowledgement delays.

Specifically and once dataflow 30 is established, sending device 24 may start transferring file 38 as groups of data packets. As discussed above, sending device 24 may attempt to continuously double the quantity of packets transferred but control process 50 may control the rate of these dataflows. For example, assume that sending device 24 sends out one-hundred-twenty-eight data packets of file 38. For the next data transfer, sending device 24 would want to transfer two-hundred-fifty-six data packets. However and as discussed above, sending device 24 will not be able to send out any more data packets until sending device 24 receives an acknowledgement of receipt of the one-hundred-twenty-eight packets. In a traditional (i.e., prior art) communication platform that does not include first acknowledgement device 18 and second acknowledgement device 20, that acknowledgement would be generated by receiving device 28 and it would take approximately 64.0 milliseconds to receive. However, in communication platform 10, that acknowledgement is generated by first acknowledgement device 18 and it could take as little as 2.0 milliseconds to receive, thus allowing the transfer rate of dataflow 30 to more efficiently ramp up.

As discussed above, control process 50 may be configured to control the transfer rate of discrete dataflows (e.g., dataflow 30) through the use of an RWND value and acknowledgement delays. As is known in the art, RWND (i.e., Receiver Window) is a TCP state variable that defines the amount of data (in packets) that the destination can receive in one operation. In typical communication platforms, that destination is receiving device 28. Therefore and in these traditional (i.e., prior art) communication platforms, the communication platform cannot control the transfer rate of the individual dataflows (as that is controlled by the receivers of the dataflows). However, since communication platform 10 includes first acknowledgement device 18 (which provides the acknowledgements of data transfers to sending device 24), communication platform 10 and control process 50 may control the transfer rate of the individual dataflows within plurality of dataflows 38.

Specifically and through the use of first acknowledgement device 18, sending device 24 can theoretically double their transfer rate every 2.0 milliseconds, as opposed to every 64.0 milliseconds in the traditional (i.e., prior art) communication platform that does not include first acknowledgement device 18. And through the use of RWND and acknowledgement delays, the transfer rates of the dataflows within plurality of dataflows 38 may be controlled.

Continuing with the above-stated example in which dataflow 30 just transmitted one-hundred-twenty-eight packets of file 38; for the next data transfer, sending device 24 would want to transfer two-hundred-fifty-six data packets. However, sending device 24 will only be able to send out as many data packets as RWND specifies they can. Additionally sending device 24 will not be able to send out any data packets until sending device 24 receives an acknowledgement of receipt from first acknowledgement device 18 concerning the one-hundred-twenty-eight data packets that were just transmitted.

Specifically and when increasing 104 the transfer rate of the dataflow (e.g., dataflow 30), control process 50 may increase 108 the RWND value associated with the dataflow (e.g., dataflow 30) and/or decrease 110 an acknowledgement delay associated with the dataflow (e.g., dataflow 30). Accordingly, control process 50 may increase 108 the RWND for dataflow 30 to e.g., two-hundred data packets, thus allowing sending device 24 to send two-hundred data packets during the next data transfer. And since control process 50 wants to increase the transfer rate of dataflow 30, control process 50 may decrease 110 (or eliminate) any acknowledgement delay associated with dataflow 30. Typically, dataflow process 10 may allow the transfer rate of e.g., plurality of dataflows 38 to be repeatedly increased until the occurrence of one or more of the conditions stated above (at which point a steady transfer rate may be retained), thus maximizing the bandwidth utilization of communication trunk 12.

And as network conditions may change over time (e.g., a load reduction on an overloaded router/switch that was dropping packets), control process 50 may periodically attempt to increase the rate of a discrete dataflow (e.g., dataflow 30) above the steady transfer rate discussed above. Referring also to FIG. 3, there is shown one embodiment of the manner in which control process 50 may attempt to increase the rate of e.g., dataflow 30. For example, control process 50 may begin (at time t1) to raise the rate of e.g., dataflow 30 until a packet loss is sensed (at time t2). At this point in time, the rate of dataflow 30 may be reduced to e.g., a level at which packet loss was not occurring.

Continuing with the above-stated example, in the event of: a loss of data packets between sending device 24 and first acknowledgement device 18 or a loss of data packets between receiving device 28 and second acknowledgement device 20; control process 50 may decrease 106 the rate of one or more dataflows within wired communication trunk 12. These losses of data packets may occur when e.g., router/switch 22 and/or router/switch 26 become overloaded and start dropping data packets (resulting in data packet loss).

Specifically and when decreasing 106 the rate of a dataflow (e.g., dataflow 30), control process 50 may decrease 112 an RWND value associated with the dataflow (e.g., dataflow 30) and/or increase 114 an acknowledgement delay associated with the dataflow (e.g., dataflow 30). Accordingly, control process 50 may decrease 112 the RWND for dataflow 30 to e.g., one-hundred data packets, thus allowing sending device 24 to send only one-hundred data packets during the next data transfer. And since control process 50 wants to decrease the transfer rate of dataflow 30, control process 50 may increase 114 any acknowledgement delay associated with dataflow 30 (e.g., by 10 milliseconds, 20 milliseconds, 30 milliseconds or 40 milliseconds), thus delaying (in milliseconds) the amount of time between when (in this example) first acknowledgement device 18 receives a quantity of data packets from sending device 24 and when first acknowledgement device 18 acknowledges receipt of that quantity of data packets.

As stated above, in the event that data packets of a discrete dataflow (e.g., dataflow 30) are being stored within e.g., second acknowledgement device 20, this is indicative of data being transferred to receiving device 28 at a rate that is quicker than receiving device 28 can handle. During operation of communication platform 10, when data packets are received on first acknowledgement device 18, they are immediately provided to second acknowledgement device 20, wherein the received data packets are stored in temporary storage (e.g., buffers) within second acknowledgement device 20. Second acknowledgement device 20 may then provide these data packets to receiving device 28 as quickly as receiving device 28 can accept them. In a manner similar to that described above, receiving device 28 may utilize RWND and acknowledgement delays to regulate the rate at which these data packets are transferred to receiving device 28. Accordingly, in the event that receiving device 28 cannot accept these data packets at the rate at which second acknowledgement device 20 is receiving them from first acknowledgement device 18, the temporary storage within second acknowledgement device 18 may begin to fill up. Accordingly, control process 10 may decrease 106 the rate of the dataflow (e.g., dataflow 30) by an amount (and for a duration) that will either a) stop the filling of the temporary storage within second acknowledgement device 20 or may b) allow for the emptying of the temporary storage within second acknowledgement device 20.

Referring also to FIG. 4, there is shown one embodiment of the manner in which control process 50 may react in response to data packets of a discrete dataflow (e.g., dataflow 30) being stored within e.g., second acknowledgement device 20. For example and upon control process 10 determining that data packets are being stored within second acknowledgement device 20; at time t1, control process 50 may reduce the transfer rate of dataflow 30 by “x” for a defined period of time (e.g., until time t2).

As discussed above, in the event that the actual bandwidth utilization of wired communication trunk 12 exceeds a target bandwidth utilization for wired communication trunk 12, control process 50 may decrease 106 the rate of one or more dataflows within wired communication trunk 12. Accordingly, control process 50 may determine 116 an actual bandwidth utilization of wired communication trunk 12. When determining 116 an actual bandwidth utilization for wired communication trunk 12, control process 50 may determine the quantity of data being transmitted from first acknowledgement device 18 to second acknowledgement device 20. Determining 116 bandwidth utilization by determining the actual data transmitted by first acknowledgement device 18 tends to be more accurate than summing the dataflows included within e.g., plurality of dataflows 38, as additional housekeeping data packets (which may be encapsulated in GRE (i.e., generic routing encapsulation) packets) may be transferred between acknowledgments devices 18, 20.

For the following example, assume that wired communication trunk 12 is a 10.00 gigabit communication trunk and the target utilization for this communication trunk is 95%. First acknowledgement device 18 would be configured/designed for the 10.00 gigabit capacity of wired communication trunk 12 and, therefore, would be aware of this 10.00 gigabit capacity. Accordingly, if control process 50 determines 116 that e.g., 9.80 gigabits of data are being transferred through wired communication trunk 12 (which is 98% and exceeds the 95% target utilization), control process 50 may decrease 106 the rate of one or more dataflows within wired communication trunk 12. Typically and when decreasing 106 data transfer rates due to over utilization of a communication trunk, the decrease will be applied to all of the dataflows included within e.g., plurality of dataflows 38. Accordingly, control process 50 may decrease 112 an RWND value associated with each dataflow included within plurality of dataflows 38 and/or increase 114 an acknowledgement delay associated with each dataflow included within plurality of dataflows 38 to reduce the utilization of wired communication trunk 12.

When controlling the rate of a dataflow within wired communication trunk 12, various variables over and above RWND and acknowledgement delay may be used to regulate the transfer rate of a dataflow. Specifically, the rate of a dataflow may be defined as follows:

${Rate} = {2^{SSCL}\left( \frac{RWND}{SMSS} \right){{LEN}\left( \frac{LRTT}{DLAY} \right)}}$

wherein:

-   -   SSCL is the receive window scaling factor, wherein when a         dataflow is established, an SSCL is defined that allows for the         exponential expansion of the default 16 bit window size;     -   RWND is the Receiver Window that is discussed above;     -   SMSS is the data size;     -   LEN is the packet size;     -   LRTT is the local round trip delay between e.g., sending device         24 and first acknowledgement device 18; and     -   DLAY is the acknowledgement delay that is discussed above.

In accordance with the above-described equation and by varying RWND and acknowledgement delays in the manner discussed above, the rate of one or more dataflows within wired communication trunk 12 may be varied/controlled.

Dataflow Prioritization Methodology:

When a plurality of dataflows (e.g., plurality of dataflows 38) are passing through wired communication trunk 12, priority may be given to certain dataflows over other dataflows. For example, dataflows concerning certain procedures may be prioritized (e.g., the restoration of a destroyed data site); dataflows concerning certain clients may be prioritized (e.g., clients offering streaming video services); and dataflows concerning certain governmental organizations may be prioritized (e.g., Police, Fire, Military, FEMA, TSA, DHS, ATF, ICE, and Amber Alerts).

Accordingly and referring also to FIG. 5, control process 50 may monitor 200 a plurality of dataflows (e.g., plurality of dataflows 38) within wired communication trunk 12 to identify 202 a set of dataflows (e.g., dataflow set 56), chosen from plurality of dataflows 38, for prioritization. Dataflow set 56 may include a single dataflow or may include a plurality of dataflows.

As discussed above and in a traditional (i.e., prior art) communication platform that does not include first acknowledgement device 18 and second acknowledgement device 20, centralized regulation of dataflows within a communication platform was not possible. However, since wired communication platform 12 includes acknowledgement devices 18, 20, control process 50 may prioritize 204 dataflow set 56.

When prioritizing 204 the set of dataflows (e.g., dataflow set 56), control process 50 may increase 206 the rate of dataflow set 56, wherein increasing 206 the rate of the set of dataflows (e.g., dataflow set 56) may include increasing 208 the RWND value associated with dataflow set 56 (in the manner described above) and/or decreasing 210 the acknowledgement delay associated with dataflow set 56 (in the manner described above).

Additionally/alternatively, when prioritizing 204 the set of dataflows (e.g., dataflow set 56), control process 50 may prevent 212 the decrease of the rate of dataflow set 56, wherein preventing 212 the decrease of the rate of the set of dataflows (e.g., dataflow set 56) may include preventing 214 a decrease of the RWND value associated with dataflow set 56 and/or preventing 216 an increase of an acknowledgement delay associated with dataflow set 56.

Data Redirection in a Bifurcated Communication Trunk Methodology:

Referring also to FIG. 6, there is shown communication platform 300 that includes a plurality of wired communication trunks, namely wired communication trunk 12, wired communication trunk 302, wired communication trunk 304, and wired communication trunk 306. As discussed above, each of communication trunks 12, 302, 304, 306 may include a pair of acknowledgement device. For example, wired communication trunk 12 is shown to include first acknowledgement device 18 and second acknowledgement device 20; wired communication trunk 302 is shown to include first acknowledgement device 308 and second acknowledgement device 310; wired communication trunk 304 is shown to include first acknowledgement device 312 (wherein a second acknowledgement device is not shown); and wired communication trunk 306 is shown to include first acknowledgement device 314 (wherein a second acknowledgement device is not shown).

As discussed above, when a dataflow (e.g., dataflow 30) is established, a triple handshake procedure may be employed, wherein sending device 24 may send a packet (e.g., synchronize (SYN) packet 32) to receiving device 28; synchronization acknowledgement (SYN-ACK) packet 34 may be received by sending device 24; and sending device 24 may send acknowledgement (ACK) packet 36 to receiving device 28; thus establishing dataflow 30.

Typically, the same wired communication trunk is used for both outbound data packets and inbound data packets. However, sometimes the outbound path may be different than the inbound path. For the following example, assume that router/switch 22 determined that the best path from sending device 24 to receiving device 28 was through wired communication trunk 12, while router/switch 26 determined that the best path from receiving device 28 to sending device 24 was through wired communication trunk 302.

Accordingly and when establishing dataflow 30, sending device 24 may send SYN packet 32 to receiving device 28 via wired communication trunk 12. However, receiving device 28 may send SYN-ACK packet 34′ to sending device 24 via wired communication trunk 302. Therefore, first acknowledgement device 308 of wired communication trunk 302 may receive SYN-ACK packet 34′ for which it did not receive a corresponding SYN packet (namely SYN packet 32 that was initially received by first acknowledgement device 18 of wired communication trunk 12 and provided to second acknowledgement device 20 of wired communication trunk 12). If this happens, problems may occur since e.g., first acknowledgement device 18 of wired communication path 12 would never receive confirmation that SYN packet 32 actually reached receiving device 28 and, therefore, first acknowledgement device 18 would never delete its stored copy of SYN packet 32. Accordingly, control process 50 may monitor activity within communication platform 300 for such a situation.

Referring also to FIG. 7, upon receiving 400 return data (e.g., SYN-ACK packet 34′) of dataflow 30 on first acknowledgement device 308 of wired communication trunk 302 within communication platform 300, control process 50 may determine if it received the corresponding forward data (namely SYN packet 32). If corresponding forward data (namely SYN packet 32) of e.g., dataflow 30 was not received on first acknowledgement device 308, control process 50 may determine 402 which acknowledgement device within communication platform 300 received the corresponding forward data (namely SYN packet 32). In this particular example and as discussed above, the acknowledgement device that received the corresponding forward data (namely SYN packet 32) was second acknowledgement device 20 of wired communication trunk 12 within communication platform 300.

When determining 402 which acknowledgement device within communication platform 300 received the corresponding forward data (namely SYN packet 32), control process 50 may broadcast 404 inquiry 316 to at least a portion of the acknowledgement devices included within communication platform 300. For example, control process 50 may broadcast 404 inquiry 316 to acknowledgement devices 20, 312, 314 included within communication platform 300. Further and when determining 402 which acknowledgement device within communication platform 300 received the corresponding forward data (namely SYN packet 32), control process 50 may receive 408 confirming response 318 from second acknowledgement device 20 of wired communication trunk 12 within communication platform 30.

Upon receiving 406 confirming response 318 from second acknowledgement device 20, control process 50 may forward 410 the return data (e.g., SYN-ACK packet 34′) to second acknowledgement device 20 of wired communication trunk 12, resulting in SYN-ACK packet 34′ being forwarded to first acknowledgement device 18 for processing (e.g., the clearing of stored packet copies, as discussed above). Further, control process 50 may redirect 412 any future data of dataflow 30 to second acknowledgement device 20 of wired communication trunk 12, wherein examples of this future data may include but is not limited to one or more of an acknowledgement (ACK) packet and a data packet.

Multi-Trunk Dataflow Regulation Methodology:

Referring also to FIG. 8, there is shown communication platform 500 that includes a plurality of wired communication trunks, namely wired communication trunks 502, 504, 506, 508, 510, 512, 514, 516. As discussed above, each of communication trunks 502, 504, 506, 508, 510, 512, 514, 516 includes a pair of acknowledgement device, wherein:

-   -   wired communication trunk 502 is shown to include first         acknowledgement device 518 and second acknowledgement device         520;     -   wired communication trunk 504 is shown to include first         acknowledgement device 522 and second acknowledgement device         524;     -   wired communication trunk 506 is shown to include first         acknowledgement device 526 and second acknowledgement device         528;     -   wired communication trunk 508 is shown to include first         acknowledgement device 530 and second acknowledgement device         532;     -   wired communication trunk 510 is shown to include first         acknowledgement device 534 and second acknowledgement device         536;     -   wired communication trunk 512 is shown to include first         acknowledgement device 538 and second acknowledgement device         540;     -   wired communication trunk 514 is shown to include first         acknowledgement device 542 and second acknowledgement device         544; and     -   wired communication trunk 516 is shown to include first         acknowledgement device 546 and second acknowledgement device         548.

Router/switch 22 may be configured to couple sending device 24 to communication platform 500 and router/switch 26 may be configured to couple receiving device 28 to communication platform 500. Further, router/switches 550, 552, 554, 556 may be configured to couple communication trunks 502, 504, 506, 508, 510, 512, 514, 516 within communication platform 500.

As discussed above, when a dataflow (e.g., dataflow 30) is established, a triple handshake procedure may be employed, wherein sending device 24 may send a packet (e.g., synchronize (SYN) packet 32) to receiving device 28; synchronization acknowledgement (SYN-ACK) packet 34 may be received by sending device 24; and sending device 24 may send acknowledgement (ACK) packet 36 to receiving device 28; thus establishing dataflow 30. However and in communication platform 500, multiple wired communication trunks must be utilized to get from sending device 24 to receiving device 28, regardless of the path chosen by the various router/switches within communication platform 500.

Accordingly and when establishing dataflow 30 through communication platform 500, various packets (e.g., SYN packet 32, SYN-ACK packet 34, ACK packet 36, and data packets) are transferred between wired communication trunks via the router/switches that couple them. Accordingly, if dataflow 30 utilized wired communication trunks 508, 510, 512, a data packet (e.g., data packet 558) being transferred from sending device 24 to receiving device 28 would occur as follows:

-   -   data packet 558 would be received by router/switch 22 and         provided to first acknowledgement device 530 (which would         acknowledge receipt of data packet 558 to sending device 24);     -   data packet 558 would be received by second acknowledgement         device 532 and provided to router/switch 554;     -   data packet 558 would be received by router/switch 554 and         provided to first acknowledgement device 534 (which would         acknowledge receipt of data packet 558 to first acknowledgement         device 530);     -   data packet 558 would be received by second acknowledgement         device 536 and provided to router/switch 556;     -   data packet 558 would be received by router/switch 556 and         provided to first acknowledgement device 538 (which would         acknowledge receipt of data packet 558 to first acknowledgement         device 534);     -   data packet 558 would be received by second acknowledgement         device 540 and provided to router/switch 26; and     -   data packet 558 would be received by router/switch 26 and         provided to receiving device 38 (which would acknowledge receipt         of data packet 558 to first acknowledgement device 538).

As discussed above, control process 50 may be configured to control the transfer rate of discrete dataflows (e.g., dataflow 30) through the use of an RWND value and acknowledgement delays. Accordingly, control process 50 and communication platform 500 needs to be configured to allow such rate control information to pass between separate and distinct wired communication trunks. In this particular example and with respect to dataflow 30, these wired communication trunks include separate and distinct wired communication trunks 508, 510, 512.

Accordingly and referring also to FIG. 9, control process 50 may generate 600 rate control information (e.g., rate control information 560) for an existing dataflow (e.g., dataflow 30) on a second acknowledgement device (e.g., second acknowledgement device 540) of a first wired communication trunk (e.g., wired communication trunk 512) within communication platform 500. As discussed above, examples of rate control information 560 may include but are not limited to the RWND value and/or the acknowledgement delays, wherein the value of RWND and the acknowledgement delays may be varied depending upon various factors such as a desired rate for a data flow, packet loss within a particular data flow, and the overall congestion of one or more of (in this example) wired communication trunks 508, 510, 512.

Control process 50 may then provide 602 rate control information 560 for dataflow 30 from second acknowledgement device 540 to first acknowledgement device 538 of wired communication trunk 512.

Control process 50 may receive 604 rate control information 560 for dataflow 30 on first acknowledgement device 538 of wired communication trunk 512 and may provide 606 rate control information 560 from first acknowledgement device 538 of wired communication trunk 512 to a second acknowledgement device (e.g., second acknowledgement device 536 of a second wired communication trunk (e.g., wired communication trunk 510) within communication platform 500.

Since the intended recipient of rate control information 560 is sending device 24, this process may be repeated until rate information 560 is received by first acknowledgement device 530, which (as discussed above) may control the rate at which sending device 24 provides data within dataflow 30.

Assume for this example that another dataflow (e.g., dataflow 562) is established that flows through wired communication trunk 516, through router/switch 554 and into wired communication trunk 510. Also suppose that just prior to the initiation of dataflow 562, wired communication trunk 510 was at 95% capacity (e.g., the target utilization for wired communication trunk 510) and the bandwidth of dataflow 562 would put the utilization of wired communication trunk over this 95% utilization target.

Accordingly and continuing with the above stated example, control process 50 may identify 608 a new dataflow (e.g., dataflow 562) within communication platform 500. If dataflow 562 can be handled by wired communication trunk 510 without being over utilized, nothing will need to change with respect to dataflow 30. However, if the addition of dataflow 562 within wired communication trunk 510 results in over utilization of wired communication trunk 510, control process 50 may decrease 610 the rate of an existing dataflow (e.g., dataflow 30) to free up bandwidth for the new dataflow (e.g., dataflow 562) within one or more of the wired communication trunks. For example, assume that the addition of dataflow 562 over-utilizes wired communication trunk 510 but does not over-utilize wireless communication trunk 512.

When decreasing 610 the rate of the existing dataflow (e.g., dataflow 30), control process 10 may decrease 612 the RWND value (as previously discussed) and/or increase 614 the acknowledgement delay (as previously discussed).

General:

As will be appreciated by one skilled in the art, the present disclosure may be embodied as a method, a system, or a computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, the present disclosure may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium.

Any suitable computer usable or computer readable medium may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. The computer-usable or computer-readable medium may also be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the present disclosure may be written in an object oriented programming language such as Java, Smalltalk, C++ or the like. However, the computer program code for carrying out operations of the present disclosure may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through a local area network/a wide area network/the Internet (e.g., network 18).

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer/special purpose computer/other programmable data processing apparatus, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowcharts and block diagrams in the figures may illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, may be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

A number of implementations have been described. Having thus described the disclosure of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the disclosure defined in the appended claims. 

What is claimed is:
 1. A computer-implemented method, executed on a computing device, comprising: monitoring a plurality of dataflows within a wired communication trunk for the occurrence of one or more conditions; and in response to the occurrence of the one or more conditions, adjusting a rate of at least one dataflow chosen from the plurality of dataflows.
 2. The computer-implemented method of claim 1 wherein adjusting a rate of at least one dataflow chosen from the plurality of dataflows includes: increasing the rate of the at least one dataflow.
 3. The computer-implemented method of claim 2 wherein increasing the rate of the at least one dataflow includes one or more of: increasing an RWND value associated with the at least one dataflow; and decreasing an acknowledgement delay associated with the at least one dataflow.
 4. The computer-implemented method of claim 1 wherein adjusting a rate of at least one dataflow chosen from the plurality of dataflows includes: decreasing the rate of the at least one dataflow.
 5. The computer-implemented method of claim 4 wherein decreasing the rate of the at least one dataflow includes one or more of: decreasing an RWND value associated with the at least one dataflow; and increasing an acknowledgement delay associated with the at least one dataflow.
 6. The computer-implemented method of claim 1 wherein the occurrence of the one or more conditions includes: the loss of packets between a sending device of the at least one dataflow and the wired communication trunk.
 7. The computer-implemented method of claim 1 wherein the occurrence of the one or more conditions includes: the loss of packets between a receiving device of the at least one dataflow and the wired communication trunk.
 8. The computer-implemented method of claim 1 wherein the occurrence of the one or more conditions includes: the storing of packets of the at least one dataflow within a gateway coupled to the wired communication trunk.
 9. The computer-implemented method of claim 1 further comprising: determining an actual bandwidth utilization of the wired communication trunk.
 10. The computer-implemented method of claim 9 wherein the occurrence of the one or more conditions includes: the actual bandwidth utilization of the wired communication trunk exceeding a target bandwidth utilization for the wired communication trunk.
 11. A computer program product residing on a computer readable medium having a plurality of instructions stored thereon which, when executed by a processor, cause the processor to perform operations comprising: monitoring a plurality of dataflows within a wired communication trunk for the occurrence of one or more conditions; and in response to the occurrence of the one or more conditions, adjusting a rate of at least one dataflow chosen from the plurality of dataflows.
 12. The computer program product of claim 11 wherein adjusting a rate of at least one dataflow chosen from the plurality of dataflows includes: increasing the rate of the at least one dataflow.
 13. The computer program product of claim 12 wherein increasing the rate of the at least one dataflow includes one or more of: increasing an RWND value associated with the at least one dataflow; and decreasing an acknowledgement delay associated with the at least one dataflow.
 14. The computer program product of claim 11 wherein adjusting a rate of at least one dataflow chosen from the plurality of dataflows includes: decreasing the rate of the at least one dataflow.
 15. The computer program product of claim 14 wherein decreasing the rate of the at least one dataflow includes one or more of: decreasing an RWND value associated with the at least one dataflow; and increasing an acknowledgement delay associated with the at least one dataflow.
 16. The computer program product of claim 11 wherein the occurrence of the one or more conditions includes: the loss of packets between a sending device of the at least one dataflow and the wired communication trunk.
 17. The computer program product of claim 11 wherein the occurrence of the one or more conditions includes: the loss of packets between a receiving device of the at least one dataflow and the wired communication trunk.
 18. The computer program product of claim 11 wherein the occurrence of the one or more conditions includes: the storing of packets of the at least one dataflow within a gateway coupled to the wired communication trunk.
 19. The computer program product of claim 11 further comprising: determining an actual bandwidth utilization of the wired communication trunk.
 20. The computer program product of claim 19 wherein the occurrence of the one or more conditions includes: the actual bandwidth utilization of the wired communication trunk exceeding a target bandwidth utilization for the wired communication trunk.
 21. A computing system including a processor and memory configured to perform operations comprising: monitoring a plurality of dataflows within a wired communication trunk for the occurrence of one or more conditions; and in response to the occurrence of the one or more conditions, adjusting a rate of at least one dataflow chosen from the plurality of dataflows.
 22. The computing system of claim 21 wherein adjusting a rate of at least one dataflow chosen from the plurality of dataflows includes: increasing the rate of the at least one dataflow.
 23. The computing system of claim 22 wherein increasing the rate of the at least one dataflow includes one or more of: increasing an RWND value associated with the at least one dataflow; and decreasing an acknowledgement delay associated with the at least one dataflow.
 24. The computing system of claim 21 wherein adjusting a rate of at least one dataflow chosen from the plurality of dataflows includes: decreasing the rate of the at least one dataflow.
 25. The computing system of claim 24 wherein decreasing the rate of the at least one dataflow includes one or more of: decreasing an RWND value associated with the at least one dataflow; and increasing an acknowledgement delay associated with the at least one dataflow.
 26. The computing system of claim 21 wherein the occurrence of the one or more conditions includes: the loss of packets between a sending device of the at least one dataflow and the wired communication trunk.
 27. The computing system of claim 1 wherein the occurrence of the one or more conditions includes: the loss of packets between a receiving device of the at least one dataflow and the wired communication trunk.
 28. The computing system of claim 21 wherein the occurrence of the one or more conditions includes: the storing of packets of the at least one dataflow within a gateway coupled to the wired communication trunk.
 29. The computing system of claim 21 further configured to perform operations comprising: determining an actual bandwidth utilization of the wired communication trunk.
 30. The computing system of claim 29 wherein the occurrence of the one or more conditions includes: the actual bandwidth utilization of the wired communication trunk exceeding a target bandwidth utilization for the wired communication trunk. 